Liferay DXP End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Liferay DXP versions. Dates read at the vendor's own lifecycle pages (liferay.com). Updated at every deploy.
Liferay DXP 2026.Q3 is supported until August 18, 2027, its end-of-support date. The next Liferay DXP version to reach end of life is 2025.Q4, on November 25, 2026. 10 of 18 tracked Liferay DXP versions are past end of life; the most recent to reach it, 2025.Q3, did so on September 2, 2026. The full Liferay DXP lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7.0 | — | Jun 15, 2016 | Jun 14, 2023 | 1221 days past EOL | EOL |
| 7.1 | — | Jul 10, 2018 | Nov 13, 2025 | 338 days past EOL | EOL |
| 7.2 | — | Jun 4, 2019 | Jun 3, 2026 | 136 days past EOL | EOL |
| 7.3 | — | Oct 13, 2020 | Oct 12, 2027 | 360 days remaining | Active |
| 7.4 | — | — | Sep 1, 2030 | 1415 days remaining | Active |
| 2023.Q3 | — | Oct 20, 2023 | Oct 19, 2024 | 728 days past EOL | EOL |
| 2023.Q4 | — | Dec 13, 2023 | Dec 12, 2024 | 674 days past EOL | EOL |
| 2024.Q1 LTS LTS | — | Mar 13, 2024 | Mar 12, 2029 | 877 days remaining | Active |
| 2024.Q2 | — | Jun 12, 2024 | Jun 11, 2025 | 493 days past EOL | EOL |
| 2024.Q3 | — | Sep 12, 2024 | Sep 11, 2025 | 401 days past EOL | EOL |
| 2024.Q4 | — | Dec 11, 2024 | Dec 10, 2025 | 311 days past EOL | EOL |
| 2025.Q1 LTS LTS | — | Feb 19, 2025 | Feb 18, 2030 | 1220 days remaining | Active |
| 2025.Q2 | — | May 28, 2025 | May 27, 2026 | 143 days past EOL | EOL |
| 2025.Q3 | — | Sep 3, 2025 | Sep 2, 2026 | 45 days past EOL | EOL |
| 2025.Q4 | — | Nov 26, 2025 | Nov 25, 2026 | 39 days remaining | Warning |
| 2026.Q1 LTS LTS | — | Mar 18, 2026 | Mar 17, 2031 | 1612 days remaining | Active |
| 2026.Q2 | — | May 13, 2026 | May 12, 2027 | 207 days remaining | Active |
| 2026.Q3 | — | Aug 19, 2026 | Aug 18, 2027 | 305 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/liferay-dxp)
Liferay DXP lifecycle status — the real story
Liferay DXP is a commercial digital experience platform built on Java. Since 2023 Liferay ships a quarterly release (2026.Q3 and so on). Under the Liferay Service Life Policy every Q1 release is a Long Term Support release with a three year Premium Support Phase followed by a two year Limited Support Phase; the other quarterly releases get one year of Premium Support and no Limited phase. The older 7.0 to 7.4 lines have four years of Premium and three years of Limited Support. Limited Support covers critical security vulnerabilities and essential updates. On this page, end of support is the end of Premium Support and end of life is the end of Limited Support (or of Premium Support where there is no Limited phase). Liferay publishes no dates for the free Community Edition.
Liferay DXP release and support pattern
3 of the 18 tracked lines are designated long-term support, which is where the longer windows sit.
Of the 18 release lines tracked, 10 are past end of life and 8 are still within support. The newest line, 2026.q3, was released August 19, 2026. The next scheduled end of life is 2025.q4 on November 25, 2026 — 39 days from this build. The longest-supported line currently published is 2026.q1, to March 17, 2031.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Liferay DXP end of life mean for your organization?
When a version of Liferay DXP reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Liferay DXP should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Liferay DXP reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Liferay DXP versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Liferay DXP has 10 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Liferay DXP is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."